home *** CD-ROM | disk | FTP | other *** search
- WGT 5.1 for Watcom C/C++ 10.x
- SHAREWARE VERSION
- by Egerter Software
-
- (Full documentation in MS Word 6.0 format, WGT5.DOC)
-
- ******************************************************************************
- Installing the Software
- -----------------------
-
- At the DOS prompt, type INSTALL and the installation program will begin.
- This program will copy all or part of the toolkit to your hard drive.
- It will create a directory called WGT5 in the root directory. Each part of
- the toolkit will have a subdirectory in the WGT5 directory.
-
- Follow the on-screen prompts to complete the installation.
-
- ******************************************************************************
- Making Example Files
- --------------------
-
- If an executable version of a source code file is not present, then
- you must build one using the included batch files. Most batch files can simply
- be run to produce the EXE, but the MAKE.BAT in the WGT5\EXAMPLES must be used
- as: MAKE wgt04 or MAKE wgt12 for example.
-
- Files in the main example directory are numbered from 01 to 70. There is one
- exception to this rule, because WGT68 has its own directory and contains 5
- versions of the program.
-
- ******************************************************************************
- **** ATTENTION WGT 4.0 Users ****
- Major Changes from WGT 4.0
- =================================
-
- New structures:
-
- extern struct {
- short xres; /* Horizontal screen resolution */
- short yres; /* Vertical screen resolution */
- short videomode; /* Current videomode */
- int videobanksize; /* Size of memory bank (VESA) */
- short (*bankswitch)(short); /* Pointer to bank switch routine (VESA) */
- } WGT_SYS;
-
- This structure contains a few important statistics which can be
- read by the user. DO NOT change these variables yourself. VIDEOMODE does
- not change when using wsetmode, only with vga256 and wvesa_init.
-
-
-
- typedef struct {
- short but; /* Mouse button being pressed */
- short mx; /* Horizontal mouse coordinate */
- short my; /* Vertical mouse coordinate */
- } callback_data;
- extern callback_data mouse;
-
- All mouse variables are now found within this structure.
-
-
-
- The scrolling library has been dramatically altered. Many routines
- now use different parameters. The basic command order has been maintained
- but should be verified against the new examples.
-
- ******************************************************************************
- CONVERTING TURBO/BORLAND C PROGRAMS TO WATCOM
-
- To convert previous WGT programs to Watcom, simply do a search and replace on:
-
- Search for Replace with *** Order is important!
- ========== ============
- int short
- long int
- but mouse.but
- mx mouse.mx
- my mouse.my
-
- far NOTHING (remove all FAR references in code)
-
-
-
- Functions Which Have Been Eliminated:
- =====================================
-
- All EMS functions
- All SB routines
- wdetectcpu
-
- ******************************************************************************
-
- Library File Changes:
- =====================
-
- All library files have been renamed to include WC indicating Watcom.
-
- WFLIC_WC.LIB -now uses memory instead of EMS, so check the include file
- for variable names and defines
-
- Old name New Name
- ******** ********
- WGT4.LIB WGT5_WC.LIB
- WSPR.LIB WSPR_WC.LIB
- WGTJOY.LIB WJOY_WC.LIB
- WGTSCROL.LIB WSCR_WC.LIB
- WGT3D.LIB WGT3D_WC.LIB
- WFILE.LIB WFILE_WC.LIB
- WGTMENU.LIB WMENU_WC.LIB
- WGTFLIC.LIB WFLIC_WC.LIB
- WGTVESA.LIB WVESA_WC.LIB
-
-
- ******************************************************************************
-
- Other Notes
- ===========
-
- - wsetscreen now works with ANY block. Clipping variables are set to match
- the image dimensions.
-
- - many DOS and BIOS functions use different structures and parameters than
- the Turbo/Borland versions. Be sure to check the manuals when trying to
- find compatibility errors (compiler warnings).
-
- - All image loading functions are capable of handling ANY size picture as
- long as the machine has enough memory to hold it. Our machines have
- 8 megs of RAM and therefore a 2900x2900 pixel image is out of reach, but
- a 2800x2800 pixel image is possible (as long as program size is small :)
-
-
-
-